BTech CSE 6th Semester · School of Computer Sciences · UPES Dehradun
No single tool does everything. A DevOps toolchain is a curated set of tools — one or more for each stage — that together automate and accelerate the path from idea to production.
Continuous Development (CD) is the first stage of the DevOps lifecycle — covering planning and coding. It emphasises short development cycles, version control discipline, and fast feedback from the codebase.
Continuous Development is the practice of continuously writing, refining, and committing code in small increments using version control, ensuring the codebase is always in a workable state and ready for the next stage of the pipeline.
CI is the practice of automatically building and testing every code commit. It is the engine that keeps the shared codebase healthy and eliminates the "integration hell" of infrequent merges.
Continuous Integration is the practice of merging developer code changes into a shared repository frequently — at least daily — where each merge triggers an automated build and test pipeline to detect problems early.
What happens on every commit →
In DevOps, testing is not a phase — it is a continuous, automated activity embedded throughout the pipeline. The goal is to get fast, reliable feedback at every stage.
Many fast unit tests at the base → fewer integration tests in the middle → very few slow UI tests at the top. This shape keeps CI pipelines fast and feedback immediate.
After code passes CI and testing, it must be packaged and shipped. Two related practices govern this — and they are often confused.
Key Deployment Strategies
Monitoring closes the feedback loop. Without observability into production, teams are flying blind. Monitoring is not optional — it is the foundation of reliability and the source of data for every improvement.
Metrics — numerical measurements over time (CPU, latency, error rate) · Logs — timestamped records of events · Traces — end-to-end journey of a request across microservices
DevSecOps extends DevOps by integrating security practices at every stage of the pipeline — not as a gate at the end, but as a shared responsibility from the first line of code.
DevSecOps stands for Development, Security, and Operations. It embeds security controls, testing, and culture into the CI/CD pipeline so that security is built in, not bolted on. The guiding principle: shift left — catch security issues as early as possible.
Shift-Left Security — Security at Every Stage
DevOps and SRE are two of the most important concepts in modern software operations. They share goals but differ in origin, structure, and how they achieve reliability.
Understanding where DevOps ends and SRE begins helps organisations decide which roles and structures to adopt as they scale their engineering organisations.
| Dimension | DevOps | SRE |
|---|---|---|
| Originated at | Industry movement (Flickr/Allspaw 2009) | Google (Ben Treynor, 2003) |
| Primary Focus | Collaboration, speed, breaking silos | Reliability, scalability, availability |
| Prescriptiveness | Principles & culture — not prescriptive | Highly specific practices and metrics |
| Team Structure | Embedded in product teams | Dedicated SRE team, serves other teams |
| Key Metrics | DORA (deploy freq, lead time, CFR, MTTR) | SLIs, SLOs, error budgets, toil % |
| Automation Goal | Automate the delivery pipeline (CI/CD) | Automate operations to reduce toil |
| On-Call Rotation | Shared "you build it, you run it" | Structured SRE on-call with runbooks |
| Incident Response | Blameless post-mortems, fast MTTR | Formal incident management, RCA docs |
| Relationship | ✓ SRE implements DevOps principles with engineering rigour — they are complementary, not competing | |
A DevOps toolchain is the full set of tools integrated together to support continuous delivery — from planning to monitoring. Each tool hands off to the next automatically.
What you should be able to explain after today's session: